Systems and methods for customizing sub-applications and dashboards in a digital huddle environment

ABSTRACT

The present systems and methods for customizing sub-applications and dashboards in a digital huddle environment are disclosed. The disclosed system and method may be employed for customizing sub-applications according to predefined options, including text, images and numbers; as well as customizing dashboards according to user requirements for showing goals progress, next meetings notifications, schedule, meetings alerts, and the like, according to the requirements of a particular team working in a digital huddle.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 15/831,107, filed Dec. 4, 2017, which is a continuation of U.S.patent application Ser. No. 14/733,447, filed Jun. 8, 2015, which claimspriority to U.S. Provisional Patent Application Ser. No. 62/008,937,filed Jun. 6, 2014, U.S. Provisional Patent Application Ser. No.62/008,888, filed Jun. 6, 2014, U.S. Provisional Patent Application Ser.No. 62/008,896, filed Jun. 6, 2014, U.S. Provisional Patent ApplicationSer. No. 62/008,916, filed Jun. 6, 2014, and U.S. Provisional PatentApplication Ser. No. 62/008,948, filed Jun. 6, 2014, all of which arehereby incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates in general to collaboration systems and,more specifically, to customizing sub-applications and dashboards in adigital huddle environment.

BACKGROUND

Conventionally, team members working on one or more projects within acompany may get together in a huddle or micro-meeting on a regular basisto share information, discuss topics, evaluate performance, identifyissues and/or solve problems collaboratively. Since the introduction ofthe huddle, whiteboards have acted as the traditional tool for storingall information collected during the active huddle session. However, itmay not be possible for all participants in a meeting to be in the samephysical location at the same time, which may create a need formodifying the current huddle methodology.

Alternatives to overcome the challenge of gathering team members atdifferent locations for a huddle may include the use of one or morecollaboration tools such as conference phone calls, video conferences,Internet relay chat (IRC), and instant messaging, among others.Nevertheless, the whiteboard is still the most commonly used tool inhuddle boards, because the aforementioned collaboration tools aregeneric ways to connect people and may not offer a consistent way to befully engaged in huddles. As a result, all team members must bephysically located in the same room in order to be fully engaged in thehuddle session.

Other alternatives to overcome the above drawbacks are systemsconfigurations that enable remote huddle collaboration between teammembers of a given project content, which may take many forms includingcontact information, calendar items, mail, audio, photos, documents, andtasks or actions. A huddle user interface may include a predefinedregion for applications that can function as a home screen for a user,providing relevant content and quick access to collaboration tools.Applications' regions provide users with a predefined view or dashboardto monitor the current state of a subset of content obtainable through acomputing device. Individual applications provide users with access toapplications, application content, remote content and/or independentfunctionality. Typically, applications regions are represented in asmall or thumbnail view that provides some minimal amount ofinformation. One or more applications regions can provide a user withthe data and tasks most likely to be relevant to the particular user.Nevertheless, it is likely that a library of applications may not meetthe requirements of every huddle board.

Conventional approaches to meetings amongst remote users fail addressall of the deficiencies of the conventional collaboration tools. A webmeeting may allow a user to share a computer desktop with another userin a remote location. But the user must select which application shouldbe presented on the computer desktop, so there is no ability to presenta page that has information from multiple sub-applications that aredynamically updated. Further, the user cannot include annotationsoverlaid on the page that are simultaneously presented to the remoteuser and also stored with that particular page such that the particularpage can be retrieved at a later date along with those annotations.

Moreover, conventional extranets are capable of sharing information froma common source, but these extranets do not offer real-timecollaboration through real-time updates and simultaneous displays toother users. Further, these conventional extranets do not utilizesub-applications that dynamically display data associated with userssimultaneously accessing the extranet. Conventional computer solutionsdo not offer the desired collaboration, real-time updating, dynamicpresentation of data, and linking of additional content to the displayeddata.

Therefore, there is still a need for a huddle user interface that allowsusers to create their own applications and optimize the presentation ofcontent within a digital huddle environment.

SUMMARY

Systems and methods for customizing sub-applications and dashboards in adigital huddle environment are disclosed. The disclosed system may beemployed for customizing sub-applications according to predefinedoptions including text, images and numbers; as well as customizingdashboards according to user requirements for showing goals progress,next meetings notifications, schedule, meetings alerts, and the like.Method for customizing sub-applications and dashboards in a digitalhuddle environment may allow customization of the sub-applicationregions according to the requirements of a particular team working in adigital huddle.

In some embodiments, a computer-implemented method comprisesidentifying, by a computer, a one or more huddle board recordsassociated with a user; providing, by a computer, a graphical userinterface webpage displaying at a user device the list of one or morehuddle board records associated the user; upon receiving from the userdevice a selection of a huddle board record through the graphical userinterface, providing, by the computer, a huddle board page to the userdevice, the huddle board page comprising a graphical user interfaceconfigured to display one or more sub-applications containing contentthat is associated with a particular sub-application; receiving, by thecomputer, from the user device, a selection of a new sub-application forinclusion to the huddle board page, the new sub-application stored in asub-application database comprising non-transitory machine-readablestorage media configured to store one or more sub-applications; upon thecomputer determining the user has access rights to add the newsub-application to the huddle board page, based upon access rights inthe huddle board record: fetching, by the computer, the newsub-application from the sub-application database, wherein the newsub-application contains content configured to be displayed according toa set of content rules associated with the new sub-application;generating, by the computer, in the huddle board record a set of accessrights for one or more users associated with the new sub-application,based upon one or more rights selections received from the user device;updating, by the computer, the graphical user interface of the huddleboard page based on the new sub-application and the set of content rulesassociated with the new sub-application; receiving, by the computer, oneor more inputs from a second computing device through the graphical userinterface configured to display the huddle board page; and updating, bythe computer, the huddle board page according to the one or more inputs,wherein the graphical user interface is configured to display real-timeupdates to the one or more sub-applications and the new sub-application,based on inputs received from one or more user computing devices.

Numerous other aspects, features and benefits of the present disclosuremay be made apparent from the following detailed description takentogether with the drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure can be better understood by referring to thefollowing figures. The components in the figures are not necessarily toscale, emphasis instead being placed upon illustrating the principles ofthe disclosure. In the figures, reference numerals designatecorresponding parts throughout the different views.

FIG. 1 is a block diagram of an exemplary system architecture for adigital huddle collaboration system, according to an embodiment.

FIG. 2 is a block diagram of exemplary components in a computing devicein which one or more embodiments of the present disclosure may operate.

FIG. 3 is a flowchart of a process for displaying a huddle boardsummary, according to an exemplary embodiment.

FIG. 4 illustrates the components of a huddle board summary, accordingto an exemplary embodiment.

FIG. 5 depicts an example of a user interface displaying a huddle boardsummary, according to an exemplary embodiment.

FIG. 6 shows options within a menu of a huddle board summary userinterface, according to an exemplary embodiment.

FIG. 7 is a flowchart of a method for customizing sub-application anddashboards in a digital huddle environment, according to an exemplaryembodiment where a user is required to add a sub-application to thehuddle board.

FIG. 8 is a flowchart of a method for customizing sub-applications anddashboards in a digital huddle environment, according to an exemplaryembodiment where a user is required to configure sub-applications afterstarting a huddle.

FIG. 9 is a flowchart of a method for customizing sub-applications anddashboards in a digital huddle environment, according to an exemplaryembodiment where a user is required to configure sub-applications afterjoining a huddle.

FIG. 10 illustrates an application of the disclosed method forcustomizing sub-applications and dashboards in a digital huddleenvironment, according to an exemplary embodiment.

DETAILED DESCRIPTION

The present disclosure is here described in detail with reference toembodiments, which form a part here. Other embodiments may be usedand/or other changes may be made without departing from the spirit orscope of the present disclosure. The illustrative embodiments describedin the detailed description are not meant to be limiting of the subjectmatter presented.

As used herein, the following terms have the following definitions:

“Huddle” refers to a group of two or more members of a project andorganizational team, brought together on a regular basis to recognizeoutstanding contributions, evaluate performance, identify issues, andsolve problems collaboratively.

“Huddle board” refers to a user interface generated by a huddlecollaboration system which may display the content collected during ahuddle in the form of one or more sub-applications.

“Active Huddle” refers to a huddle board which a leader may have startedand to which one or more participants may join remotely through a huddlecollaboration system.

“Huddle summary” refers to a user interface generated by a huddlecollaboration system which may show one or more sub-applications in thehuddle board, and each sub-application may display a summary-level viewof the data it may contain.

“Leader” refers to a team member that may initiate and manage a huddlesession. A leader may have an additional set of permissions that mayinclude for example, the ability to create huddle boards, configure orotherwise modify a huddle session, among others.

“Sub-application” refers to a software tool that may enable remotecollaboration between authenticated team members in a digital huddleenvironment.

“User's Huddle Boards” refers to a user interface generated by a huddlecollaboration system which may display a list of the user's huddleboards in which he/she may be participating in, and a list of publicboards which may be viewed by anyone in the company.

Some embodiments provide a system that may allow for customizingsub-applications and dashboards in a digital huddle environment. Thesystem may employ data management systems and methods in order to allowa user to customize application regions and dashboards of a digitalhuddle user interface.

Additionally, the present disclosure relates to a method for customizingsub-applications and dashboards in a digital huddle environment. Themethod for customizing sub-applications and dashboards in a digitalhuddle environment may include a system that may be used to processusers customization options applying a huddle management system capableperform and keep record of the user preferences. The disclosed methodmay use internal information sources.

In some embodiments, an aspect of the present disclosure is acomputer-implemented system for customizing sub-applications anddashboards in a digital huddle environment that may use informationsources, such as one or more internal databases, and a huddle managementsystem including one or more software modules, such as one or moremodule managers, one or more authentication modules, one or more dataprocessing modules, and one or more sub-applications modules. The systemmay also include a user interface on which a customer may interact withthe system by means of a computing device, such as smartphones, desktopcomputers, laptop computers, tablets, and PDAs, among others.

Another aspect of the present disclosure is a computer-implementedmethod for customizing sub-applications and dashboards in a digitalhuddle environment.

In another embodiment, the disclosed method may be employed when a useremploys a computing device to access an options menu to customizesub-applications and dashboards after accessing the huddle boardsummary. A central processing unit may execute the disclosed method,which may include a user selecting, by means of a computing device, anoptions menu of huddle board summary user interface; the user selecting,by means of a computing device, to add a sub-application from theoptions menu; a huddle management system verifying the user'scredentials; huddle management system checking if the user is thehuddle's leader; a huddle management system allowing the huddle's leaderto select a sub-application to add, if huddle management systemidentifies the entered credentials as ones belonging to a huddle'sleader; the huddle management system checking if the leader has grantedthe user permission to edit the huddle board, if huddle managementsystem does not identifies the entered credentials as ones belonging toa huddle's leader; the huddle management system allowing the user toenter again the credentials to verify the user's credentials again, ifhuddle management system does not recognizes that the leader has grantedthe user permission to edit; the huddle management system allowing theuser to select a sub-application to add, if huddle management systemrecognizes that the leader has granted the user permission to edit; theuser selecting, by means of a computing device, a standardsub-application; a sub-applications module displaying a small view ofthe selected sub-application; the user selecting, by means of acomputing device, a standard sub-application; the sub-applicationsmodule displaying a large view of the selected sub-application; the userediting, by means of a computing device, the title, content, size,format, among others, of the selected sub-application; a module managerrecording the user's preferences in an internal database; and the huddlemanagement system displaying an updated huddle board summary.

In other embodiments, the disclosed method may be employed when a useremploys a computing device to access an options menu to customizesub-applications and dashboards after starting a huddle session. Acentral processing unit may execute the disclosed method, which mayinclude a user selecting, by means of a computing device, an optionsmenu of a huddle board summary; the user electing, by means of acomputing device, to start a huddle; a huddle management systemverifying the user's credentials, checking if the user is the huddle'sleader; the huddle management system displaying an updated huddle boardsummary, if huddle management system identifies the entered credentialsas ones belonging to a huddle's leader; the huddle management systemchecking if the leader has granted the user permission to activate ahuddle session, if huddle management system does not identifies theentered credentials as ones belonging to a huddle's leader; the huddlemanagement system allowing the user to enter again the credentials toverify the user's credentials again, if huddle management system doesnot recognizes that the leader has granted the user permission toactivate a huddle session; the huddle management system displaying anupdated huddle board summary, if huddle management system recognizesthat the leader has granted the user permission to activate a huddlesession; the user selecting, by means of a computing device, asub-application to edit from the huddle board summary; the huddlemanagement system verifying the user's credentials; the huddlemanagement system checking if the user is the huddle's leader; thehuddle management system checking if the huddle's leader has granted theuser permission to edit the huddle board during an activated huddlesession, if huddle management system does not identifies the enteredcredentials as ones belonging to a huddle's leader; the huddlemanagement system allowing the user to enter again the credentials toverify the user's credentials again, if huddle management system doesnot recognize that the leader has granted the user permission to edit; asub-applications module highlighting the customizable sub-applications,if huddle management system identifies the entered credentials as onesbelonging to a huddle's leader; the user editing, by means of acomputing device, the title, content, size, and format, among others, ofthe selected sub-application; a module manager recording the user'spreferences in an internal database; and the huddle management systemdisplaying an updated huddle board summary.

In further embodiments, the disclosed method may be employed when a useremploys a computing device to access an options menu to customizesub-applications and dashboards after joining a huddle session. Acentral processing unit may execute the disclosed method, which mayinclude a user selecting, by means of a computing device, the optionsmenu of a huddle board summary; the user electing, by means of acomputing device, to join a huddle from the options menu; a huddlemanagement system verifying the user's credentials; the huddlemanagement system checking if the user has permission to join the activehuddle session; the huddle management system displaying an updatedhuddle board summary, if huddle management system identifies the enteredcredentials as ones belonging to a user with permission to join theactive huddle session; the huddle management system allowing the user toenter again the credentials again, if huddle management system does notidentifies the entered credentials as ones belonging to a user withpermission to join the active huddle session; a user selecting, by meansof a computing device, a sub-application to edit from the huddle boardsummary; the huddle management system verifying the user's credentials;the huddle management system checking if the huddle's leader has grantedthe user permission to edit the huddle board during an activated huddlesession; huddle management system allowing the user to enter again thecredentials to verify the user's credentials again, if huddle managementsystem does not recognize that the leader has granted the userpermission to edit; a sub-applications module highlighting thecustomizable sub-applications, if huddle management system recognizesthat the leader has granted the user permission to edit the huddle boardduring an activated huddle session; the user editing, by means of acomputing device, the title, content, size, and format, among others, ofthe selected sub-application; a module manager recording the user'spreferences in an internal database; and the huddle management systemdisplaying an updated huddle board summary.

Exemplary System Architecture for Customizing Sub-Applications andDashboards in a Digital Huddle Environment

FIG. 1 is a block diagram of an exemplary system architecture 100 for adigital huddle collaboration system, according to an embodiment. Thedisclosed system architecture 100 may include different components whichmay dynamically interact with each other through network connections102. Network connections 102 may refer to any suitable connectionbetween computers, such as for example intranets, local area networks(LAN), virtual private networks (VPN), wireless area networks (WAN), andthe internet, among others.

System architecture 100 may include one or more computing hardwaresuitable for executing the components within system architecture 100,according to embodiments described here. In addition, each component maybe executed by a server, a single computer, or multiple computers in adistributed configuration.

System architecture 100 may include one or more internal databases 104and a huddle management system 106, among other components. Internaldatabase 104 may store data generated by one or more software modulesoperating within huddle management system 106, data and files uploadedby a user such as a team leader or a team participant, and thecredential of each authorized user of the company to allow them toaccess and modify huddle boards, among others.

Internal database 104 may grant access to huddle management system 106when needed, and may be implemented through known in the art databasemanagement systems (DBMS), such as, for example, MySQL, PostgreSQL,SQLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE,FoxPro, IBM DB2, LibreOffice Base, FileMaker Pro, and/or any other typeof database that may organize collections of data.

According to an embodiment, huddle management system 106 may beoperatively coupled to one or more internal databases 104 throughnetwork connections 102, and may include one or more authenticationmodules 108, one or more data processing modules 110, one or more modulemanagers 112, one or more sub-applications modules 114, and any othersuitable software module required for the proper operation of huddlemanagement system 106. Each software module within huddle managementsystem 106 may include a processing unit for running related algorithmsor computer executable program instructions that may be executed by aserver, a single computer, or multiple computers in a distributedconfiguration; and may be configured to interact with one or moresoftware modules of the same or different type operating within huddlemanagement system 106. Each processing unit may include a processor withcomputer-readable medium, such as a random access memory (RAM) coupledto the processor. Examples of a processor may include a microprocessor,an application specific integrated circuit (ASIC), and a fieldprogrammable object array (FPOA), among others.

Huddle management system 106 may generate a suitable user interface 116on a client computing device 118 through which a user, such as a teamleader and/or a team participant, may interact with one or more softwaremodules operating within huddle management system 106. The computingdevice 118 may be any computer type device such as smartphones, desktopcomputers, laptop computers, tablets, PDAs, and/or another type ofprocessor-controlled device that may receive, process, and/or transmitdigital data. In addition, user interface 116 may be configured tocollect information from one or more internal databases 104, and receiveand/or feed information to one or more users interacting with computingdevice 118.

Huddle management system 106 may be operated by one or more algorithmsand/or one or more set of computer executable program instructions forintegrating operation with module manager 112 in a software module thatmay allow multiple inputs and outputs from internal database 104, and/orany other suitable sources.

According to some embodiments of the present disclosure, huddlemanagement system 106 may generate user interface 116 which may requestand/or collect information from one or more client computing devices 118interacting with user interface 116 via an input device, such as a touchscreen, a mouse, a keyboard, a keypad, and others. Authentication module108 may receive the user's credentials through client computing device118 and may validate them in order to assign authorization to access,activate, edit, and/or manage one or more huddle boards and/orsub-applications in the huddle board. Data processing module 110 mayreceive and process information collected during an active huddlesession, and may store this information in internal database 104 whenneeded. Data processing module 110 may also be configured toautomatically retrieve information requested by one or more clientcomputing devices 118 and/or one or more software modules, where thisinformation may be obtained from internal database 104 and/or thesuitable operation of one or more software modules operating withinhuddle management system 106. Module manager 112 may interact with oneor more software modules operating within huddle management system 106,may control the operation of huddle collaboration system, and mayprocess requests from one or more client computing devices 118 and/orone or more software modules, among other activities. Huddle managementsystem 106 may generate user interface 116 which may display the contentof a huddle to one or more users in the form of one or moresub-applications (not shown in FIG. 1). Internal database 104 may storeany suitable data generated from the operation of one or more softwaremodules within huddle management system 106 and may make it availablefor further analysis performed by one or more software modules withinhuddle management system 106, and/or one or more users.

Sub-applications module 114 may be employed in the display of a suitableuser interface 116 on a client computing device 118, so that a user,such as a team leader and/or a team participant, may interact withhuddle management system 106 allowing for the user to performcustomization of the sub-applications regions according to therequirements of the user's team working in a digital huddle. Clientcomputing device 118 may be any computer type device such assmartphones, desktop computers, laptop computers, tablets, PDAs, and/oranother type of processor-controlled device that may receive, process,and/or transmit digital data. Data derived from the user customizationof sub-applications regions or dashboards may be stored in internaldatabase 104 in order to keep record of the user preferences.

The system architecture 100 may allow for one or more client computingdevice 118, displaying a graphical user interface 116 configured toreceive information from the system architecture 100, to request and/orfeed information dynamically through the interaction of the clientcomputing device 118 with different software modules. Examples of clientcomputing devices 118 may include smartphones, desktop computers, laptopcomputers, tablets, and PDAs, among others.

In some embodiments, one or more software modules included in the systemarchitecture 100 of the present disclosure may include one or moresearch engines, written in a suitable programming language for executingqueries and retrieving required information, designed to use one or moresets of information related to one or more huddle sessions. The searchengine may be written in a suitable programming language for executingqueries and retrieving required information. The search engine may alsomine data through internal database 104. The search engine may beexecuted in any suitable computing device, server, or any other suitablecomputing hardware and/or may be operated by one or more algorithmsand/or one or more set of instructions for integrating operations withsystem architecture 100.

FIG. 2 is a block diagram of exemplary components in a computing device200 in which one or more embodiments of the present disclosure mayoperate.

According to some embodiments, computing device 200 may correspond to aserver, a client computing device, a smartphone, a desktop computer, alaptop computer, a tablet, a PDA, and/or another type ofprocessor-controlled device that may receive, process, and/or transmitdigital data, among others. Computing device 200 may include a bus 202,an input/output device 204, a communication interface 206, a memory 208,a storage device 210, and a CPU 212 (central processing unit). In otherembodiments, computing device 200 may include additional, fewer,different, or differently arranged components than are illustrated inFIG. 2.

Bus 202 may include a path that permits components within computingdevice 200 to communicate with each other. Input/output device 204 mayinclude peripherals and/or other mechanisms that may enable a user toinput information to computing device 200, including for example akeyboard, a mouse, a button, a touch screen, voice recognition, andbiometric mechanisms, among others. Input/output device 204 may alsoinclude a mechanism that may output information to the user of computingdevice 200 such as, for example, a display, a light emitting diode(LED), and a speaker, among others. Communication interface 206 mayinclude mechanisms that may enable computing device 200 to communicatewith other computing devices and/or systems through network connections.Network connections may refer to any suitable connections betweencomputers such as, for example, intranets, local area networks (LAN),virtual private networks (VPN), wireless area networks (WAN) and theinternet among others. Memory 208 may include a random access memory(RAM) or another type of dynamic storage device 210 that may storeinformation and instructions for execution by CPU 212. Storage device210 may include a magnetic and/or optical recording medium such asread-only memory, flash memory, ferroelectric RAM (F-RAM) hard disks,floppy disks, and optical discs, among others. CPU 212 may include amicroprocessor, an application specific integrated circuit (ASIC), and afield programmable gate array (FPGA), among others, that may interpretand execute instructions.

According to some embodiments of the present disclosure, at least onecomputing device 200, such as a server and a client computing device,among others, may perform certain operations to conduct huddles remotelyand that may be required for the proper operation of a huddlecollaboration system. Client computing devices and a server, amongothers, may perform these operations in response to CPU 212 executingsoftware instructions contained in a computer-readable medium, such asmemory 208.

The software instructions may be read into memory 208 from anothercomputer-readable medium, such as storage device 210, or from anothercomputing device via communication interface 206. The softwareinstructions contained in memory 208 may cause CPU 212 to perform one ormore suitable processes which may be further described later.Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedhere. Thus, implementations described here are not limited to anyspecific combination of hardware circuitry and software.

Exemplary Method for Customizing Sub-Applications and Dashboards in aDigital Huddle Environment

FIG. 3 is a flowchart of a process 300 for displaying a huddle boardsummary on the user interface of a computing device, according to anexemplary embodiment.

Process 300 for remote huddle collaboration may be executed, forexample, by a huddle collaboration system as shown in FIG. 1, which mayinclude different components that may dynamically interact with eachother through network connections.

Process 300 for remote huddle collaboration may start when a user, suchas a huddle leader or a huddle participant within a company, may access302 the website of a huddle collaboration system using a clientcomputing device. This huddle collaboration system may generate a loginscreen as an initial user interface, through which the user may enter304 his/her company's credentials, via an input device such as a touchscreen, a mouse, a keyboard, a keypad, and others. If the authenticationmodule operating within huddle management system of huddle collaborationsystem can validate 306 the user's credentials, then, the huddlecollaboration system may display 308 the user's huddle boards that mayinclude a list of the huddle boards in which he/she may be participatingin and a list of public boards, where these public boards may be viewedby anyone in the company and may be edited by authorized users.Otherwise, the huddle collaboration system may request the user to enter304 his/her credentials at least one more time.

Users may select 310 from their huddle board list, a huddle board theymay wish to participate in via an input device, and then, the huddlecollaboration system may display the selected huddle board summary 312which may show all the sub-applications in the selected huddle board,and each sub-application may display a summary-level view of the data itcontains. Sub-applications that may be shown in the user's huddlesummary may be text-based, image-based or numeric-based, and mayinclude, but is not limited to, recognition, morale, announcements, keyprojects, dates/calendar, field metrics, company news (e.g. FYI newsfeed), leader standard work, employee sentiment, and customer sentiment,among others.

The user's huddle boards may also provide users with a feature which mayallow them to search for huddle boards that may not be displayed in thelist and for which they may have authorized access, and a feature whichmay allow authorized users to select from a menu 314 and elect 316 tocreate a new huddle board via an input device. When users elect 316 tocreate a new huddle board, the huddle management system may display ahuddle board summary 312 of the new huddle.

FIG. 4 illustrates the components 400 of a huddle board summary,according to an exemplary embodiment. Components 400 of a huddle boardsummary may include standard sub-applications 402 and customsub-applications 404.

When a user selects via an input device a huddle board from a huddleboard list, the huddle management system may display a huddle boardsummary.

Huddle board summary user interface may be executed by a huddlecollaboration system as shown in FIG. 1, which may include differentcomponents that may dynamically interact with each other through networkconnections.

According to some embodiments of the present disclosure, huddle boardsummary user interface may enable one or more users, such as a huddleleader and a huddle participant of a company, to preview all thesub-applications in the huddle board, and each sub-application maydisplay a summary-level view of the data it may contain. Huddle boardsummary may include sub-applications that may be executed by asub-applications module. Sub-applications may provide meaningful data bysurfacing key metrics from a sub-application's detailed view. Huddleboard summary may include standard sub-applications 402 and customsub-applications 404, among others.

Standard sub-applications 402 may contain pre-defined content and have astandard layout and may speed data consumption. Examples of standardsub-applications 402 may include, but not be limited to, morale,recognition, announcements, company news (e.g. FYI news feed), anddates/calendar, among others.

Custom sub-applications 404 may be text-based, image-based, and/ornumeric-based, and may include configurable content, title, layout, andmay also have configurable metrics that allow for personalization ofcontent. Examples of custom sub-applications 404 may include keyprojects, dates/calendar, custom data tables, field metrics, leaderstandard work, customer sentiment, and employee sentiment, among others.Custom sub-applications 404 may be customized by a user, such as ahuddle's leader, who may be able to decide which sub-applications may beshown, according to the user's and/or project's requirements. Accordingto other embodiments, a user accredited as administrator may configurethe coding of any suitable sub-application within the huddle boardaccording to the project's requirements.

In an active huddle session, the huddle leader may be the only memberallowed to customize sub-applications in the huddle board which may beavailable to the huddle leader according to the huddle requirementsduring the active huddle session.

Authorized users may access, by means of a computing device, the huddleboard summary interface to change a sub-application position within thehuddle board summary space to optimize presentation of content to users.Users may specifically position sub-applications within the huddle boardsummary. For example, a user may employ a computing device to groupsub-applications associated with work-related projects in the lower leftportion of the huddle board summary while grouping sub-applicationsassociated with a user's personal life in the upper right portion of thehuddle board summary. Additionally, custom sub-applications 404 may alsobe available for an authorized user to add, by means of a computingdevice, to the huddle board summary choosing from a sub-applicationslibrary. A computing device may be used to edit the addedsub-application to fit the user requirements. Moreover, if the libraryof sub-applications does not meet the requirements of a user, the usermay access an options menu to create a sub-application (e.g.spreadsheet, images, fill-able calendar), which may be completelycustomizable; for example, the user may choose the type ofsub-application, data included, title, and layout, among others.

In huddle board summary, the team leader may have authorization to editand/or manage the configuration of the huddle board which provides theteam leader with control over the sub-applications that the teamparticipants may use in the huddle board, the name of thesesub-applications, and any other suitable configuration of thesub-applications which may satisfy the huddle board requirements. Theteam participants may use the sub-applications authorized by the teamleader for the huddle board, and may have editing and/or viewing rightsover one or more sub-applications but may be restricted from editing theconfiguration of any sub-application. In addition, one or moresub-applications may be controlled by the system and a user, such as ateam leader or a team participant, may have viewing rights but may berestricted from editing the configuration of the sub-application.

In addition, huddle board summary user interface may include an optionsmenu 406 which may enable users to access a sub-applications librarythat may allow them to use and/or add one or more sub-applications tothe huddle board. Huddle leaders may be allowed create and/orpersonalize sub-applications and control to which extent each teamparticipant may have authorization to create and/or personalize one ormore sub-applications.

Options menu 406 in huddle board summary may also allow users to join ahuddle board, in which one team member may act as a leader of the huddleand the rest of the team members may act as participants. The leader ofthe huddle may start the session to conduct a huddle and the huddleparticipants may join the huddle board after the leader has started thehuddle.

FIG. 5 depicts an example of a user interface 500 displaying a huddleboard summary, according to an exemplary embodiment.

When a user elects to create a board via an input device a huddle boardfrom a huddle board list, the huddle management system may display ahuddle board summary with empty sub-applications. The sub-applicationsmay show prompts designed to encourage users to enter data.

Huddle board summary user interface 500 may be executed by a huddlecollaboration system as shown in FIG. 1, which may include differentcomponents that may dynamically interact with each other through networkconnections.

Huddle collaboration system may generate a suitable user interface 500through which a user, such as a team leader and/or a team participant,may interact with one or more software modules operating within huddlemanagement system by means of a client computing device. The clientcomputing device may be any computer type device such as smartphones,desktop computers, laptop computers, tablets, PDAs, and/or another typeof processor-controlled device that may receive, process, and/ortransmit digital data. In addition, user interface may be configured tocollect information from one or more internal databases, and receiveand/or feed information to one or more users interacting with a clientcomputing device.

According to some embodiments of the present disclosure, a huddle boardsummary may include sub-applications which may be a part of standard orpreselected set of sub-applications for every user's huddle such asmorale 502, recognition 504, announcements 506, and company news 508(e.g. FYI news feed), among others.

Morale 502 may be an image and text-based sub-application which may beused by each team member to indicate their feeling before every huddle,by selecting an image from a library and expressing an optionalstatement of, for example, less than 140 characters. Recognition 504 maybe a text-based sub-application which may be used as a place where teammembers can recognize with a statement of, for example, less than 140characters, anyone they have worked with for exceptional work.Announcements 506 may be a text-based sub-application which may be usedfor team members to share important events and/or news with the rest ofthe team. Company news 508 may be text-based which may provide news andalerts relevant to all the company's employees and may also providesignificant news that should be communicated to all the huddle membersduring an active huddle session. In other embodiments, thesub-applications may also include a dates/calendar sub-application thatmay be a fillable calendar which may be used as a place for team membersto share important dates with one another such as out of office dates,team meeting dates, and others.

In various embodiments, the sub-applications may show prompts surfacedto encourage users to enter data. For example, the prompt included inmorale 502 may be “How are you today? Be the first to update yourmorale!” while the prompt included in recognition 504 may be “Pay itforward. Be the first to recognize someone today!”

Huddle board summary may also include sub-applications which may becustomized by the user, who may be able to decide which sub-applicationsmay be shown, according to the user's and/or project's requirements.These sub-applications may include Key projects 510, field metrics 512,and others. Key projects 510 may be a text-based sub-application whichmay be used as a place to store and track important information abouteach of the team's key projects. Field metrics 512 may be an image,text, and number-based sub-application which may be used as a place todisplay figures shared by another business area. In other embodiments,sub-applications may also include, for example, leader standard work andemployee sentiment. Leader standard work may be a text-basedsub-application which may be used to record the progress on standardwork efforts. Employee sentiment may be a text-based sub-applicationwhich may be used to view the results of employee surveys.

Custom sub-applications may also be available for an authorized user toadd, by means of a computing device, to the huddle board summarychoosing from a sub-applications library. A computing device may be usedto edit the added sub-application to fit the user requirements.Moreover, if the library of sub-applications does not meet therequirements of a user, the user may access an options menu to create asub-application (e.g. Spreadsheet, images, fillable calendar), which maybe completely customizable; for example, the user may choose the type ofsub-application, data included, title, and layout, among others. Huddleleaders may be allowed to add, create, and/or personalizesub-applications and control to which extent each team participant mayhave authorization to add, create, and/or personalize one or moresub-applications.

Huddle board summary user interface 500 may show a text legend which mayindicate a next huddle 514 scheduled. Additionally, huddle board summaryuser interface 500 may include an options menu 406 which may enableusers to access a sub-applications library that may allow them to useand/or add one or more sub-applications to the huddle board. Optionsmenu 406 may provide huddle members with features that may allow them toadd a sub-application to the huddle board, return to home screen, andview changes made to the huddle board as news feed, among others.

FIG. 6 shows options 600 within a menu of a huddle board summary userinterface, according to an exemplary embodiment.

According to an embodiment huddle board summary user interface mayinclude menu options 600. When selected, the menu may “push” the pagecontents to the left (as shown in FIG. 6) to reveal the available menuoptions 600. The menu may be manually closed, and may closeautomatically once a selection has been made.

Options 600 may include home 602, start 604, join 606, add asub-application 608, help 610, log-out 612, and view profile 614, amongothers.

FIG. 7 is a flowchart of a method 700 for customizing sub-applicationand dashboards in a digital huddle environment, according to anexemplary embodiment where a user is required to add a sub-applicationto the huddle board.

After users select a huddle board from their huddle board list, thehuddle collaboration system may display the selected huddle boardsummary 312. Huddle board summary user interface may include an optionsmenu which the user may select 702 by means of a computing device. Acomputing device may be any computer type device such as smartphones,desktop computers, laptop computers, tablets, PDAs, and/or another typeof processor-controlled device that may receive, process, and/ortransmit digital data.

The user may use a computing device to select to add 704 asub-application from the options menu. Add a sub-application option mayallow users to personalize current sub-applications and to createsub-applications from generic sub-applications, according to the huddlerequirements. Huddle leaders may be allowed to create and/or personalizesub-applications and control to which extent each team participant mayhave authorization to create and/or personalize one or moresub-applications.

Subsequently, huddle management system may verify 706 the user'scredentials to determine if the user may have authorization to access an“add a sub-application” option. First, huddle management system maycheck 708 if the user is the huddle's leader. If huddle managementsystem identifies the entered credentials as ones belonging to ahuddle's leader, huddle management system may allow the huddle's leaderto select a sub-application 710 to add. If huddle management system doesnot identifies the entered credentials as ones belonging to a huddle'sleader, huddle management system may check 712 if the leader has grantedthe user permission to edit the huddle board. If huddle managementsystem does not recognizes that the leader has granted the userpermission to edit, huddle management system may allow the user to enteragain the credentials to verify 706 the user's credentials again. Ifhuddle management system recognizes that the leader has granted the userpermission to edit, huddle management system may allow the user toselect a sub-application 710 to add.

If the user employs a computing device to select a standard 714sub-application, huddle management system may execute a sub-applicationsmodule to display a small 716 view of the selected sub-application whilea module manager may record 718 the user's preferences in an internaldatabase. Subsequently, huddle management system may display an updated720 huddle board summary.

If the user does not select a standard 714 sub-application, huddlemanagement system may execute a sub-applications module to display alarge 722 view of the selected sub-application. Large 722 view maycontain customizable content and may have a configurable layout.Afterwards, the user may edit 724 the title, content, size, format,among others, of the selected sub-application. Subsequently, a modulemanager may record 718 the user's preferences in an internal database.Then, huddle management system may display an updated 720 huddle boardsummary. Huddle management system may allow a user to delete asub-application if necessary.

In other embodiments, huddle management system may also verify if a userhas additional permissions, which may allow to configure the coding ofany suitable sub-application within the huddle board.

In other embodiments, huddle management system may also verify if a userhas additional permissions, which may allow the user to configure thecoding of any suitable sub-application within the huddle board.

FIG. 8 is a flowchart of a method for customizing sub-applications anddashboards in a digital huddle environment, according to an exemplaryembodiment where a user is required to configure sub-applications 800after starting a huddle.

After users select a huddle board from their huddle board list, thehuddle collaboration system may display the selected huddle boardsummary 312. Huddle board summary user interface may include an optionsmenu which the user may select 802 by means of a computing device. Acomputing device may be any computer type device such as smartphones,desktop computers, laptop computers, tablets, PDAs, and/or another typeof processor-controlled device that may receive, process, and/ortransmit digital data.

The user may use a computing device to elect to start 804 a huddle fromthe options menu. Start 804 a huddle option may allow to activate asession to conduct a huddle and the huddle participants may join thehuddle board after the leader has started the huddle. While in an activesession, only a huddle leader may be allowed to create and/orpersonalize sub-applications and control to which extent each teamparticipant may have authorization to create and/or personalize one ormore sub-applications. A huddle leader may start the huddle and mayconduct it by viewing and/or editing the content in the huddle, andhuddle participants may engage in the huddle by viewing the contentwhich the huddle leader may be showing during the huddle session.

In an active huddle session, the huddle leader may be the only memberallowed to customize sub-applications in the huddle board which may beavailable to the huddle leader according to the huddle requirementsduring the active huddle session. Sub-applications that may becustomizable during the active huddle board session may be one or acombination of text-based, image-based, or numeric-based, and mayinclude, but is not limited to, key projects, dates/calendar, fieldmetrics, company news, leader standard work, employee sentiment, andcustomer sentiment, among others. In addition, the active huddle boardmay provide huddle leaders with features that may allow the team leaderto record a problem, capture screen shots, return to home screen, viewchanges made to the huddle board as a news feed, mark up the screen,erase annotations that may have been made using the markup feature, havea video call with huddle members, and chat with other huddle members,among others.

Subsequently, huddle management system may verify 806 the user'scredentials to determine if the user may have authorization to activatea huddle session. First, huddle management system may check 808 if theuser is the huddle's leader. If huddle management system identifies theentered credentials as ones belonging to a huddle's leader, huddlemanagement system may display 810 an updated huddle board summary. Ifhuddle management system does not identifies the entered credentials asones belonging to a huddle's leader, huddle management system may check812 if the leader has granted the user permission to activate a huddlesession. If huddle management system does not recognize that the leaderhas granted the user permission to activate a huddle session, huddlemanagement system may allow the user to enter again the credentials toverify 806 the user's credentials again. If huddle management systemrecognizes that the leader has granted the user permission to activate ahuddle session, huddle management system may display 810 an updatedhuddle board summary.

After displaying the updated huddle board summary, the user may identifya requirement 814 to edit, and may subsequently use a computing deviceto select 816 a sub-application to edit from the huddle board summary.

Subsequently, huddle management system may verify 818 the user'scredentials to determine if the user may have authorization to editduring an activated huddle session. First, huddle management system maycheck 820 if the user is the huddle's leader. If huddle managementsystem identifies the entered credentials as ones belonging to ahuddle's leader, huddle management system may execute sub-applicationsmodule to highlight 822 the customizable sub-applications. If huddlemanagement system does not identify the entered credentials as onesbelonging to a huddle's leader, huddle management system may check 824if the huddle's leader has granted the user permission to edit thehuddle board during an activated huddle session. If huddle managementsystem does not recognize that the leader has granted the userpermission to edit, huddle management system may allow the user to enteragain the credentials to verify 818 the user's credentials again. Ifhuddle management system recognizes that the leader has granted the userpermission to edit the huddle board during an activated huddle session,huddle management system may execute sub-applications module tohighlight 822 the customizable sub-applications.

Afterwards, the user may employ a computing device to edit 826 thetitle, content, size, format, among others, of the selectedsub-application. Subsequently, a module manager may record 828 theuser's preferences in an internal database. Then, huddle managementsystem may display an updated 830 huddle board summary.

In other embodiments, huddle management system may also verify if a userhas additional permissions, which may allow to configure the coding ofany suitable sub-application within the huddle board.

FIG. 9 is a flowchart of a method for customizing sub-applications anddashboards in a digital huddle environment, according to an exemplaryembodiment where a user is required to configure sub-applications 900after joining a huddle.

Options menu in a huddle board summary may also allow users to join ahuddle board, in which one team member may act as a leader of the huddleand the rest of the team members may act as participants. The leader ofthe huddle may start the session to conduct a huddle and the huddleparticipants may join the huddle board after the leader has started thehuddle. If the huddle participants join the huddle board before thehuddle leader starts the huddle, they may access a waiting screen untilthe huddle leader starts the huddle session.

After users select a huddle board from their huddle board list, thehuddle collaboration system may display the selected huddle boardsummary 312. Huddle board summary user interface may include an optionsmenu. By means of a computing device, the user may select 902 theoptions menu. A computing device may be any computer type device such assmartphones, desktop computers, laptop computers, tablets, PDAs, and/oranother type of processor-controlled device that may receive, process,and/or transmit digital data.

The user may employ a computing device to elect 904 to join a huddlefrom the options menu. Join a huddle option may allow accessing anactive huddle session. Subsequently, huddle management system may verify906 the user's credentials to determine if the user may haveauthorization to join the active huddle session. First, huddlemanagement system may check 908 if the user has permission to join theactive huddle session. If huddle management system identifies theentered credentials as ones belonging to a user with permission to jointhe active huddle session, huddle management system may display 910 anupdated huddle board summary. If huddle management system does notidentify the entered credentials as ones belonging to a user withpermission to join the active huddle session, huddle management systemmay allow the user to enter again the credentials to verify 906 theuser's credentials again.

After displaying the updated huddle board summary, the user may identifya requirement 912 to edit and subsequently use a computing device toselect 914 a sub-application to edit from the huddle board summary.

Subsequently, huddle management system may verify 916 the user'scredentials to determine if the user may have authorization to editduring an activated huddle session. First, huddle management system maycheck 918 if the huddle's leader has granted the user permission to editthe huddle board during an activated huddle session. If huddlemanagement system does not recognize that the leader has granted theuser permission to edit, huddle management system may allow the user toenter again the credentials to verify 916 the user's credentials again.If huddle management system recognizes that the leader has granted theuser permission to edit the huddle board during an activated huddlesession, huddle management system may execute sub-applications module tohighlight 920 the customizable sub-applications.

Afterwards, the user may employ a computing device to edit 922 thetitle, content, size, format, among others, of the selectedsub-application. Subsequently, a module manager may record 924 theuser's preferences in an internal database. Then, huddle managementsystem may display an updated 926 huddle board summary.

In other embodiments, huddle management system may also verify if a userhas additional permissions, which may allow to configure the coding ofany suitable sub-application within the huddle board.

FIG. 10 illustrates an application 1000 of the disclosed method forcustomizing sub-applications and dashboards in a digital huddleenvironment, according to an exemplary embodiment.

Example #1 is an application of the disclosed method 700 for customizingsub-applications and dashboards in a digital huddle environment,according to an exemplary embodiment.

In some embodiments, a user may identify the requirement to edit a keyprojects sub-application and select the key projects sub-application ofthe huddle board summary. Then, as shown in FIG. 10, huddle managementsystem may display a detailed view of the key projects sub-application.In the detailed view, huddle management system may display a tableincluding projects in which the team is involved. Huddle managementsystem may allow a user to employ a computing device to select a cell.When a cell is selected, huddle management system may execute asub-applications module to allow a user to edit the content of the cell.Additionally, the sub-applications module may display a menu that mayallow a user to edit the character, paragraph, or grid of the cell.

The foregoing method descriptions and the interface configuration areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe steps in the foregoing embodiments may be performed in any order.Words such as “then,” “next,” etc. are not intended to limit the orderof the steps; these words are simply used to guide the reader throughthe description of the methods. Although process flow diagrams maydescribe the operations as a sequential process, many of the operationscan be performed in parallel or concurrently. In addition, the order ofthe operations may be re-arranged. A process may correspond to a method,a function, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination may correspond to a return ofthe function to the calling function or the main function.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedhere may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

Embodiments implemented in computer software may be implemented insoftware, firmware, middleware, microcode, hardware descriptionlanguages, or any combination thereof. A code segment ormachine-executable instructions may represent a procedure, a function, asubprogram, a program, a routine, a subroutine, a module, a softwarepackage, a class, or any combination of instructions, data structures,or program statements. A code segment may be coupled to another codesegment or a hardware circuit by passing and/or receiving information,data, arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. may be passed, forwarded, or transmitted via anysuitable means including memory sharing, message passing, token passing,network transmission, etc.

The actual software code or specialized control hardware used toimplement these systems and methods is not limiting of the invention.Thus, the operation and behavior of the systems and methods weredescribed without reference to the specific software code beingunderstood that software and control hardware can be designed toimplement the systems and methods based on the description here.

When implemented in software, the functions may be stored as one or moreinstructions or code on a non-transitory computer-readable orprocessor-readable storage medium. The steps of a method or algorithmdisclosed here may be embodied in a processor-executable software modulewhich may reside on a computer-readable or processor-readable storagemedium. A non-transitory computer-readable or processor-readable mediaincludes both computer storage media and tangible storage media thatfacilitate transfer of a computer program from one place to another. Anon-transitory processor-readable storage media may be any availablemedia that may be accessed by a computer. By way of example, and notlimitation, such non-transitory processor-readable media may compriseRAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other tangible storagemedium that may be used to store desired program code in the form ofinstructions or data structures and that may be accessed by a computeror processor. Disk and disc, as used here, include compact disc (CD),laser disc, optical disc, digital versatile disc (DVD), floppy disk, andBlu-ray disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers. Combinations of the aboveshould also be included within the scope of computer-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentinvention. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedhere may be applied to other embodiments without departing from thespirit or scope of the invention. Thus, the present invention is notintended to be limited to the embodiments shown here but is to beaccorded the widest scope consistent with the following claims and theprinciples and novel features disclosed here.

What is claimed is:
 1. A computer-implemented method comprising:generating, by a computer, a huddle session for an interaction between aplurality of users, wherein each user of the plurality of users isassociated with one or more huddle board records, and wherein each ofthe one or more huddle board records corresponds to one or moresub-applications stored in a sub-application library accessible duringthe huddle session from a huddle board summary; receiving, by thecomputer, a selection of the one or more sub-applications stored in thesub- application library for display from at each respective user deviceof each of the plurality of users interacting with the huddle boardsummary, at least one of the selected one or more sub-applicationsdisplays data related to the huddle session and metrics related to aproject; transmitting, by the computer, a huddle board pagecorresponding to the huddle session at the user device of each of theplurality of users, wherein the huddle board page displays the one ormore selected sub-applications, wherein at least one of the selected oneor more sub-applications is operated via the huddle board page anddisplays huddle session data associated with the respectivesub-application on the huddle board page and the metrics related to theproject; receiving, by the computer, from a first user device of a firstuser of the plurality of users, a selection of a new sub-application forinclusion to the huddle board page during the huddle session;determining, by the computer, whether the first user has access rightsto add the new sub-application to the huddle board page based upon averification of whether the first user generated the huddle session oraccessed the huddle session based upon credentials associated with thefirst user stored in a huddle board record; authenticating, by thecomputer, the first user as having a permission to edit the huddle boardpage based upon the verification of the credentials associated with thefirst user; responsive to determining that the new sub-application addedto the huddle board is customizable, editing, by the computer, based onan editing request received from the first user device, the newsub-application to change an attribute of the new sub-application; andupdating, by the computer, the huddle board page with the newsub-application to generate an updated huddle board page during thehuddle session, wherein a graphical user interface of each user deviceof the plurality of users displays the updated huddle board pageincluding the one or more sub-applications and the new sub-applicationwith the change of the attribute provided by the first user device. 2.The computer-implemented method of claim 1, wherein the newsub-application is stored in a sub-application database comprisingnon-transitory machine-readable storage media configured to store one ormore new sub-applications.
 3. The computer-implemented method of claim1, wherein the computer facilitates editing of the one or moresub-applications upon the computer determining that the first usergenerated the huddle session.
 4. The computer-implemented method ofclaim 1, wherein the computer facilitates editing of the one or moresub-applications upon the computer determining that the first user isauthorized based upon access rights in the huddle board record.
 5. Thecomputer-implemented method of claim 1, wherein the first userauthorizes one or more other users of the plurality of users in thehuddle session for editing the one or more sub-applications in thehuddle board page.
 6. The computer-implemented method of claim 1,wherein the first user edits a title, content, size, and a format of theone or more sub-applications displayed on the huddle board page.
 7. Thecomputer-implemented method of claim 1, further comprising generating,by the computer, a set of access rights for one or more new usersassociated with the new sub-application, based upon one or more rightsselections received from the first user device.
 8. Thecomputer-implemented method of claim 7, further comprising storing, bythe computer, the set of access rights for the one or more new usersassociated with the new sub-application in the huddle board record. 9.The computer-implemented method of claim 1, further comprising:receiving, by the computer, one or more inputs from a second userdevice; and updating, by the computer, the huddle board page accordingto the one or more inputs to display real-time updates to the one ormore sub-applications and the new sub-application, based on the one ormore inputs received from the second user device.
 10. A systemcomprising: a computer configured to: generate a huddle session for aninteraction between a plurality of users, wherein each user of theplurality of users is associated with one or more huddle board records,and wherein each of the one or more huddle board records corresponds toone or more sub-applications stored in a sub-application libraryaccessed during the huddle session from a huddle board summary; receivea selection of the one or more sub-applications stored in thesub-application library for display from a user device of each of theplurality of users interacting with the huddle board summary, at leastone of the selected one or more sub-applications displays data relatedto the huddle session and metrics related to a project; transmit ahuddle board page corresponding to the huddle session at the user deviceof each of the plurality of users, wherein the huddle board pagedisplays the one or more selected sub-applications, wherein the one ormore sub-applications is operated via the huddle board page and displayshuddle session data associated with the respective sub-application onthe huddle board page and the metrics related to the project; receivefrom a first user device of a first user of the plurality of users, aselection of a new sub-application for inclusion to the huddle boardpage during the huddle session; determine whether the first user hasaccess rights to add the new sub-application to the huddle board pagebased upon a verification of whether the first user generated the huddlesession or accessed the huddle session based upon credentials associatedwith the first user stored in a huddle board record; authenticate thefirst user as having a permission to edit the huddle board page basedupon the verification of the credentials associated with the first user;responsive to determining that the new sub-application added to thehuddle board is customizable, edit, based on an editing request receivedfrom the first user device, the new sub-application to change anattribute of the new sub-application; and update the huddle board pagewith the new sub-application to generate an updated huddle board pageduring the huddle session, wherein a graphical user interface of eachuser device of the plurality of users displays the updated huddle boardpage including the one or more sub-applications and the newsub-application with the change of the attribute provided by the firstuser device.
 11. The system of claim 10, wherein the new sub-applicationis stored in a sub-application database comprising non-transitorymachine-readable storage media configured to store one or more newsub-applications.
 12. The system of claim 10, wherein the computerfacilitates editing of the one or more sub-applications upon thecomputer determining that the first user generated the huddle session.13. The system of claim 10, wherein the computer facilitates editing ofthe one or more sub-applications upon the computer determining that thefirst user is authorized based upon access rights in the huddle boardrecord.
 14. The system of claim 10, wherein the first user authorizesone or more other users of the plurality of users in the huddle sessionfor editing the one or more sub-applications in the huddle board page.15. The system of claim 10, wherein the first user edits a title,content, size, and a format of the one or more sub-applicationsdisplayed on the huddle board page.
 16. The system of claim 10, whereinthe computer is configured to generate a set of access rights for one ormore new users associated with the new sub-application, based upon oneor more rights selections received from the first user device.
 17. Thesystem of claim 16, wherein the computer is configured to store the setof access rights for the one or more new users associated with the newsub-application in the huddle board record.
 18. The system of claim 10,wherein the computer is configured to receive one or more inputs from asecond user device; and update the huddle board page according to theone or more inputs to display real-time updates to the one or moresub-applications and the new sub-application, based on the one or moreinputs received from the second user device.